Systems and methods for operating a bridge server to support multiple shards of a blockchain

ABSTRACT

Systems and methods for operating a bridge server to support multiple shards of blockchains are disclosed. The multiple shards may be used to record ownership rights of in-game digital assets. The in-game digital assets may be usable in an online gaming platform. Exemplary implementations may: execute an instance of a game; maintain user accounts for the users of a blockchain on a first and a second decentralized ledger server; record sets of rights pertaining to sets of digital assets; receive an exchange request for a first digital asset; receive transferal information for the first digital asset; transfer sets of instructions to the first and second decentralized ledger servers such that the first decentralized ledger server removes the first digital asset from the first set of digital assets and the second decentralized ledger server adds the first digital asset to the second set of digital assets.

FIELD OF THE DISCLOSURE

The present disclosure relates to systems and methods for operating abridge server to support multiple shards of blockchains, the multipleshards being used to record ownership rights of in-game digital assets,the in-game digital assets being usable in an online gaming platform.

BACKGROUND

Online gaming platforms are known. Users of online gaming platformsexchanging digital in-game assets to other users is known. Decentralizedledgers are known.

SUMMARY

One aspect of the present disclosure relates to a system configured foroperating a bridge server to support multiple shards of blockchains. Themultiple shards may be used to record ownership rights of in-gamedigital assets. The in-game digital assets may be usable in an onlinegaming platform. The system may include an online gaming platform, afirst decentralized ledger server, a second decentralized ledger server,a bridge server, and/or other components. The online gaming platform maybe configured to host one or more games. The online gaming platform maybe provided, at least in part, by one or more game servers that includeone or more processors configured by machine-readable instructions. Theprocessors may be configured to execute an instance of a first onlinegame to facilitate presentation of the first online game to users, andimplement in-game actions in the instance of the first online game inresponse to action requests for the in-game actions by the users. Thepresentation of the first online game may include the presentation ofviews of the first online game that are determined using informationgenerated by execution of the instance of the first online game. Theusers may include a first user and a second user that interact with theonline gaming platform. The first decentralized ledger server may beconfigured to implement a first node of a first shard of a firstblockchain. The first decentralized ledger server may include one ormore processors configured by machine-readable instructions to (i)maintain user accounts for the users of the first blockchain, includingthe first user and the second user; (ii) record, on the first shard, afirst set of rights pertaining to a first set of digital assets, whereinthe recorded first set of rights reflect ownership of a first digitalasset by the first user, wherein the first digital asset is usablewithin the online gaming platform; and (iii) receive instructions tomodify the recorded first set of rights. The second decentralized ledgerserver may be configured to implement a second node of a second shard ofthe first blockchain. The second decentralized ledger server may includeone or more processors configured by machine-readable instructions to(i) maintain user accounts for the users of the first blockchain,including the first user and the second user; (ii) record, on the secondshard, a second set of rights pertaining to a second set of digitalassets, wherein the recorded second set of rights reflect ownership of asecond digital asset by the first user, wherein the second digital assetis usable within the online gaming platform; and (iii) receiveinstructions to modify the recorded second set of rights. The bridgeserver may include one or more processors configured by machine-readableinstructions. The bridge server may receive, from the first user, anexchange request that indicates the first user offers the first digitalasset for a first transferal to one of the users. The bridge server mayreceive transferal information regarding the first transferal of thefirst digital asset from the first user to the second user. The bridgeserver may, responsive to receipt of the transferal information,transfer a first set of instructions to the first decentralized ledgerserver and a second set of instructions to the second decentralizedledger server. The one or more processors of the first decentralizedledger server may be configured to (i) receive the first set ofinstructions from the bridge server, and (ii) in accordance with thereceived first set of instructions, remove the first digital asset fromthe first set of digital assets, such that the recorded first set ofrights on the first shard no longer reflect the ownership of the firstdigital asset by the first user. The one or more processors of thesecond decentralized ledger server are further configured to (i) receivethe second set of instructions from the bridge server, and (ii) inaccordance with the received second set of instructions, add the firstdigital asset to the second set of digital assets, such that therecorded second set of rights on the second shard reflect the ownershipof the first digital asset by the second user.

Another aspect of the present disclosure relates to a method foroperating a bridge server to support multiple shards of blockchains. Themultiple shards may be used to record ownership rights of in-gamedigital assets. The in-game digital assets may be usable in an onlinegaming platform. The method may include executing an instance of a firstonline game to facilitate presentation of the first online game tousers, and implementing in-game actions in the instance of the firstonline game in response to action requests for the in-game actions bythe users, wherein the presentation of the first online game includesthe presentation of views of the first online game that are determinedusing information generated by execution of the instance of the firstonline game, wherein the users include a first user and a second userthat interact with the online gaming platform. The method may includemaintaining, by a first decentralized ledger that implements a firstnode of a first shard of a first blockchain, user accounts for the usersof the first blockchain, including the first user and the second user.The method may include recording, on the first shard, a first set ofrights pertaining to a first set of digital assets, wherein the recordedfirst set of rights reflect ownership of a first digital asset by thefirst user, wherein the first digital asset is usable within the onlinegaming platform. The method may include receiving, by the firstdecentralized ledger, instructions to modify the recorded first set ofrights. The method may include maintaining, by a second decentralizedledger that implements a second node of a second shard of the firstblockchain, user accounts for the users of the first blockchain,including the first user and the second user. The method may includerecording, on the second shard, a second set of rights pertaining to asecond set of digital assets, wherein the recorded second set of rightsreflect ownership of a second digital asset by the first user, whereinthe second digital asset is usable within the online gaming platform.The method may include receiving, by the second decentralized ledger,instructions to modify the recorded second set of rights. The method mayinclude receiving, from the first user, an exchange request thatindicates the first user offers the first digital asset for a firsttransferal to one of the users. The method may include receivingtransferal information regarding the first transferal of the firstdigital asset from the first user to the second user. The method mayinclude, responsive to receipt of the transferal information,transferring a first set of instructions to the first decentralizedledger server and a second set of instructions to the seconddecentralized ledger server. The method may include receiving the firstset of instructions. The method may include, in accordance with thereceived first set of instructions, removing the first digital assetfrom the first set of digital assets, such that the recorded first setof rights on the first shard no longer reflect the ownership of thefirst digital asset by the first user. The method may include receivingthe second set of instructions. The method may include, in accordancewith the received second set of instructions, adding the first digitalasset to the second set of digital assets, such that the recorded secondset of rights on the second shard reflect the ownership of the firstdigital asset by the second user.

Another aspect of the present disclosure relates to a system foroperating a bridge server to support multiple shards of blockchains. Thesystem may include an online gaming platform, a bridge server, and/orother components. The online gaming platform may be configured to hostone or more games. The online gaming platform may be provided, at leastin part, by one or more game servers that include one or more processorsconfigured by machine-readable instructions. The processors may beconfigured to execute an instance of a first online game to facilitatepresentation of the first online game to users, and implement in-gameactions in the instance of the first online game in response to actionrequests for the in-game actions by the users, wherein the presentationof the first online game includes the presentation of views of the firstonline game that are determined using information generated by executionof the instance of the first online game, wherein the users include afirst user and a second user that interact with the online gamingplatform. The bridge server may include processors configured tointeract with a first node that is dedicated to a first shard of a firstblockchain. The first shard (i) maintains user accounts for the users ofthe first blockchain, including for the first user and the second user,(ii) records a first set of rights pertaining to a first set of digitalassets, wherein the recorded first set of rights reflect ownership of afirst digital asset by the first user, wherein the first digital assetis usable within the online gaming platform, and (iii) receivesinstructions from the bridge server to modify the recorded first set ofrights. The bridge server may include processors configured to interactwith a second node that is dedicated to a second shard of the firstblockchain. The second shard (i) maintains user accounts for the usersof the first blockchain, including for the first user and the seconduser, (ii) records a second set of rights pertaining to a second set ofdigital assets, wherein the recorded second set of rights reflectownership of a second digital asset by the first user, wherein thesecond digital asset is usable within the online gaming platform, and(iii) receives instructions from the bridge server to modify therecorded second set of rights. The bridge server may be configured toreceive, from the first user, an exchange request that indicates thefirst user offers the first digital asset for a first transferal to oneof the users. The bridge server may be configured to receive transferalinformation regarding the first transferal of the first digital assetfrom the first user to the second user. The bridge server may beconfigured to, responsive to receipt of the transferal information,transfer a first set of instructions to the first node and a second setof instructions to the second node. The first node may (i) receive thefirst set of instructions from the bridge server, and (ii) in accordancewith the received first set of instructions, remove the first digitalasset from the first set of digital assets, such that the recorded firstset of rights on the first shard no longer reflect the ownership of thefirst digital asset by the first user. The second node may (i) receivethe second set of instructions from the bridge server, and (ii) inaccordance with the received second set of instructions, add the firstdigital asset to the second set of digital assets, such that therecorded second set of rights on the second shard reflect the ownershipof the first digital asset by the second user.

As used herein, any association (or relation, or reflection, orindication, or correspondency) involving platforms, servers, processors,shards, nodes, client computing platforms, assets, exchanges,transferals, offers, transactions, interactions, in-game actions,rights, benefits, ownership, users, accounts, metrics, metric values,scores, periods, instructions, operations, determinations,distributions, presentations, notifications, and/or another entity orobject that interacts with any part of the system and/or plays a part inthe operation of the system, may be a one-to-one association, aone-to-many association, a many-to-one association, and/or amany-to-many association or “N”-to-“M” association (note that “N” and“M” may be different numbers greater than 1).

As used herein, the term “obtain” (and derivatives thereof) may includeactive and/or passive retrieval, determination, derivation, transfer,upload, download, submission, and/or exchange of information, and/or anycombination thereof. As used herein, the term “effectuate” (andderivatives thereof) may include active and/or passive causation of anyeffect, both local and remote. As used herein, the term “determine” (andderivatives thereof) may include measure, calculate, compute, estimate,approximate, generate, and/or otherwise derive, and/or any combinationthereof.

These and other features, and characteristics of the present technology,as well as the methods of operation and functions of the relatedelements of structure and the combination of parts and economies ofmanufacture, will become more apparent upon consideration of thefollowing description and the appended claims with reference to theaccompanying drawings, all of which form a part of this specification,wherein like reference numerals designate corresponding parts in thevarious figures. It is to be expressly understood, however, that thedrawings are for the purpose of illustration and description only andare not intended as a definition of the limits of the invention. As usedin the specification and in the claims, the singular form of “a”, “an”,and “the” include plural referents unless the context clearly dictatesotherwise.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a system configured for operating a bridge server tosupport multiple shards of blockchains, in accordance with one or moreimplementations.

FIG. 2 illustrates a method for operating a bridge server to supportmultiple shards of blockchains, in accordance with one or moreimplementations.

FIG. 3 illustrates an exemplary timing diagram of actions as may occurin a system as described, in accordance with one or moreimplementations.

FIGS. 4A-4B illustrate exemplary blockchains as may be used by a systemconfigured for operating a bridge server to support multiple shards ofblockchains, in accordance with one or more implementations.

DETAILED DESCRIPTION

FIG. 1 illustrates a system 100 configured for operating a bridge server115 to support multiple shards 121 of blockchain(s) 117, in accordancewith one or more implementations. Individual blockchains 117 may includemultiple shards 121 such that individual shards 121 can independentlycomplete at least some types of transactions, without significantcomputational costs for other shards of the same individual blockchain117. Accordingly, the capacity for completing (at least some types of)transactions may increase as the number of shards increases (andprovided that the communication overhead for communication betweenshards and synchronization among shards is limited so that thecorresponding detrimental effect of this communication on thetransactional capacity is less than the increase gained in transactionalcapacity due to sharding). As used in the examples in this disclosure,individual blockchains 117 may include 2 or 3 shards, but that number isexemplary and not intended to be limiting. In some implementations,individual blockchains 117 may include 3, 4, 5, 10, 50, 100, 500, 1000,or more shards. The communication overhead may be handled and/orperformed by bridge server 115.

In some implementations, blockchain 117 may be maintained by adistributed computing platform (not shown in FIG. 1). In someimplementations, the distributed computing platform may be implementedby a set of client computing platforms and/or servers (including, forexample, one or more decentralized ledger servers 111). The distributedcomputing platform may support a virtual machine (not shown in FIG. 1).The distributed computing platform and/or the virtual machine may form aruntime environment for smart contracts and/or other executable code. Insome implementations, the distributed computing platform may includeelectronic storage configured to store part or all of blockchain 117.The smart contracts may be stored on blockchain 117. In someimplementations, the distributed computing platform may be the EOSIOplatform. In some implementations, the distributed computing platformmay be Ethereum. In some implementations, the distributed computingplatform may be similar to Ethereum. In some implementations, thevirtual machine may be a decentralized virtual machine.

Blockchain 117 may be configured to record rights pertaining to digitalassets. A given (digital) asset may be owned by a particular user. Anasset may include anything of material value or usefulness that is ownedby or on behalf of one or more users. In some implementations, a virtualitem (that may be used within gaming platform 105 and/or may be usefulwithin gaming platform 105) may be represented by a digital asset thatis recorded on blockchain 117. In some implementations, a rightpertaining to an object (e.g., a distribution right) may be an asset,the object being a physical or a virtual item. Multiple rights may forma set of rights or a bundle of rights that may be transferred and/orotherwise acted on and/or operated on together. For example, rights mayinclude one or more of a right to use, a right to sell, a right todestroy, a right to certain types of distributions, and/or other rights.For example, in some implementations, rights pertaining to a virtualitem (e.g., ownership) may be recorded on blockchain 117.

In some implementations, tokens may be a type of asset. In someimplementations, tokens may include one or more of security tokens,utility tokens, payment tokens, initial coin offering (ICO) tokens,virtual currency tokens, crypto tokens, ERC-20 tokens, EOS tokens,and/or other tokens. In some implementations, tokens not only representvalue, but may have a specific use in a particular distributed computingplatform, e.g., in the operation of blockchain 117.

In some implementations, blockchain 117 may register transactions thatmodify ownership (and/or other rights) pertaining to digital assets. Asmart contract may implement a (type of) digital asset. In someimplementations, once a smart contract has been added to a blockchain,the smart contract may be referred to as published, posted, registered,and/or recorded. Elements of blockchain 117 may be grouped together inunits that are referred to as blocks. For example, an individual blockmay include one or more assets and one or more transactions. Forexample, an individual block may be linked to one or more otherindividual blocks. Individual blocks may be linked or chained togetherto form a structure of blocks and/or a hierarchy of blocks, such as,e.g., a chain of blocks. An individual block may include one or moreassets, one or more transactions, and/or other information.

In some implementations, blockchain 117 may be publicly accessible andappend-only. In some implementations, existing blocks of blockchain 117can substantially not be altered or deleted, unless multiple copies arealtered. This is unlikely to happen provided that the multiple copiesstored on different computing platforms, e.g., in different geographicallocations. Blockchain 117 may be replicated on multiple computingplatforms, preferably in multiple different geographical locations.Additionally, individual blocks may be linked together in a manner thatprevents tampering, such as, e.g., using a hash chain and/or digitalsignatures. In particular, hash values may be generated usingfixed-output-length one-way hashing functions that take variable-lengthinput, and may be effectively impossible (or, at least, computationallyinfeasible) to reverse. As such, a hashing function may provide one-wayencryption. By way of non-limiting example, the hashing function may beSHA-256, BLAKE2, SHAKE256, and/or another hashing function. Contents ofindividual blocks, transactions, and/or assets may be digitally signedin a manner that proves integrity and/or prevents tampering, e.g., byproviding authentication.

In some implementations, blockchain(s) 117 and/or multiple shards 121 ofthese blockchain(s) 117 may be used to record ownership rights ofin-game digital assets, including but not limited to digital assets thatare not fungible. The in-game digital assets may be usable in an onlinegaming platform 105. In some implementations, system 100 may beconfigured to control bridge server 115 to support and/or interact withmultiple nodes 119 that are dedicated to shards 121 of blockchain(s)117. In some implementations, digital assets may be (or represent)virtual items that are usable within one or more online gaming platforms105. For example, some digital assets may represent user-controllablethree-dimensional in-game characters that can interact with othervirtual items within online gaming platform 115. In someimplementations, virtual items may include one or more of weapons, toys,characters, abilities, skills, tools, pets, clothing, vehicles, gamelevels, missions, assignments, chapters, tasks, mini-games, restrictedareas within a virtual space, restricted modes of gameplay, accessrights within an online game, and/or other virtual items. In someimplementations, virtual items may refer to any item or object withingaming platform 105 that a user may use, own, sell, trade, destroy,and/or otherwise effectuate a change of ownership of.

As used herein, a digital asset is fungible if it is functionally and/orotherwise indistinguishable from another digital asset. For example, apayment token such as a Bitcoin may be a fungible digital asset. Adigital asset may be non-fungible if it is unique, or one-of-a-kind. Forexample, a specific individual CryptoKitty™ may be a non-fungibledigital asset. A digital asset may be semi-fungible if there is a set ofa limited number of similar but distinguishable digital assets. Forexample, a limited-edition Blanko™ or another in-game character may be asemi-fungible digital asset. For example, one of a limited number of2-dimensional or 3-dimensional in-game virtual items may be asemi-fungible digital asset. For example, a digital ticket to a show,concert, exhibition, and/or other event may be a semi-fungible digitalasset. For example, a piece of art or jewelry (e.g., as a virtual itemor as representing a physical item) may be a semi-fungible digitalasset. As used herein, both non-fungible and semi-fungible digitalassets are considered as “notfungible” digital assets. In someimplementations, semi-fungible digital assets may share the same orsimilar data as other digital assets, but have at least a uniqueidentifier, and/or other distinguishable asset-specific information.

In some implementations, digital assets may be usable within one or moregames. Instances of the games may be executed within one or more onlinegaming platforms 105. As used herein, online gaming platform 105 mayrefer to either an individual game (e.g., an interactive online game), atype of gaming console and its ecosystem, and/or both. Online gamingplatform 105 may be operated, hosted, and/or owned by one or morestakeholders of online gaming platform 105. For example, a platformoperator (and/or another stakeholder) may sell digital in-game assets(e.g., characters, weapons, resources, etc.) to users 123 of onlinegaming platform 105. However, such a sale is not a player-to-playerexchange. In some implementations, the term “exchanges” may refer toplayer-to-player actions that facilitate individual players to auction,sell, purchase, trade, barter, transfer, and/or otherwise exchangedigital assets. In other words, individual players may own individualvirtual items, and exchange these items with other individual players byvirtue of the systems and methods described in this disclosure. Due toan exchange, ownership of a digital asset transitions from an originalowner to a new owner (even if there may, in some implementations, be oneor more intermediary and/or temporary owners during the process ofperforming the exchange). In some implementations, player-to-playerexchanged may be considered non-commercial, since there may be nocommercial interest in such a transaction, nor a commercial partyinvolved as a principal participant to the transaction.

In some implementations, a particular blockchain 117 (that, e.g.,registers in-game digital assets and/or ownership rights thereof) may besharded into different shards 121 in different ways. In someimplementations, individual shards may be user-specific (or rather,specific to a subset of users) such that an individual user account uses(or corresponds to) a particular shard, and a different user accountuses a different shard. In some implementations, individual shards maybe asset-specific (or rather, specific to a subset of in-game assets)such that an individual in-game asset uses (or corresponds to) aparticular shard, and a different in-game asset uses a different shard.In some implementations, individual shards may be game-specific (orrather, specific to a subset of the games hosted within online gamingplatform 105) such that an individual game uses (or corresponds to) aparticular shard, and a different game uses a different shard. Forexample, in a user-specific shard, a set of in-game assets may beshared, synced, and/or otherwise operative on multiple shards (and,e.g., a particular user account is using just one shard). For example,in an asset-specific shard, a set of users (or rather, a set of useraccounts) may be shared, synced, and/or otherwise operative on multipleshards (i.e., the same users or user accounts are used on multipleshards, and, e.g., a particular asset is registered on just one shard).For example, in a game-specific shard, a set of users (or rather, a setof user accounts) may be shared, synced, and/or otherwise operative onmultiple shards (i.e., the same users or user accounts may be used onmultiple shards, and, e.g., assets for a particular game are registeredon just one shard). In some implementations, a particular shard may beboth user-specific and asset-specific, or, e.g., both game-specific andasset-specific.

In some implementations, system 100 may include one or more of an bridgeserver 115, one or more online gaming platforms 105, one or moredecentralized ledger servers 111, one or more online exchange platforms127, electronic storage 130, one or more servers 102, one or more clientcomputing platforms 104, one or more user interfaces 125, one or moreexternal resources 138, and/or other components. Users 123 (alsoreferred to as players) may include one or more of a first user, asecond user, a third user, a fourth user, and/or other users.

Server(s) 102 may be configured to communicate with one or more clientcomputing platforms 104 according to a client/server architecture and/orother architectures. Client computing platform(s) 104 may be configuredto communicate with other client computing platforms via server(s) 102and/or according to a peer-to-peer architecture and/or otherarchitectures. Users 123 may access system 100 via client computingplatform(s) 104.

In some implementations, system 100 and/or server(s) 102 may beconfigured to communicate with one or more of online gaming platform(s)105, decentralized ledger server(s) 111, bridge server 115, users 123,and/or other components. Users 123 may include players who play and/orotherwise interact on online gaming platform 105. In someimplementations, online gaming platform 105 may include an online storeor exchange that facilitates exchanges of digital assets. In someimplementations, users can exchange digital assets (such as, e.g.,in-game virtual items) through one or more external exchange platforms127, including but not limited to eBay™.

Bridge server 115 may include one or more of electronic storage 130,server(s) 102, processor(s) 132, machine-readable instructions 106,and/or other components. Server(s) 102 may be configured bymachine-readable instructions 106. Machine-readable instructions 106 mayinclude one or more instruction components. The instruction componentsmay include computer program components. The instruction components mayinclude one or more of a game component 108, an interaction component110, a record component 112, an account component 113, an instructioncomponent 114, an exchange request component 116, a rights component118, a node component 120, a transferal component 124, a translatecomponent 126, a transfer component 128, an authorization component 136,and/or other instruction components. The depiction in FIG. 1 of certaincomponents being arranged, organized, and/or otherwise included in othercomponents is merely exemplary, and not intended to be limiting.

In some implementations, online gaming platforms 105 may include one ormore of electronic storage 130 c, server(s) 102 (not depicted in FIG.1), processor(s) 132 c, machine-readable instructions 106 c, and/orother components. Electronic storage 130 c may be similar to electronicstorage 130 as described elsewhere in this disclosure, though includedin online gaming platforms 105. Processor(s) 132 c may be similar toprocessor(s) 132 as described elsewhere in this disclosure, thoughincluded in online gaming platforms 105. Machine-readable instructions106 c may be similar to machine-readable instructions 106 as describedelsewhere in this disclosure, though included in online gaming platforms105.

In some implementations, decentralized ledger server(s) 111 may includeone or more decentralized ledger servers, including but not limited todecentralized ledger server 111 a, decentralized ledger server 111 b,and so forth. Decentralized ledger server 111 a and decentralized ledgerserver 111 b may include similar elements. For example, decentralizedledger server 111 a may include one or more of electronic storage 130 a,server(s) (not depicted in FIG. 1), processor(s) 132 a, machine-readableinstructions 106 a, and/or other components.

In some implementations, an individual decentralized ledger server(e.g., decentralized ledger server 111 a) may include (e.g., implement)one or more blockchains 117. For example, the individual decentralizedledger server may be dedicated to a particular blockchain 117, which maybe a private and/or permissioned blockchain.

In some implementations, an individual decentralized ledger server(e.g., decentralized ledger server 111 a) may include one or more nodes119 of one or more blockchains 117. For example, the individualdecentralized ledger server may be dedicated to a particular node 119 ofa particular blockchain 117. Typically, different nodes are included in(or implemented by, or hosted by) different servers or differentcomputer systems to increase the safety and security of transactions ona blockchain. The consensus protocol used for a particular blockchainmay be harder to falsify or circumvent when the different nodes are indifferent geographical locations, on different types of computingplatforms, and/or otherwise distributed and diverse.

In some implementations, an individual decentralized ledger server(e.g., decentralized ledger server 111 a) may include one or more shards121 of one or more blockchains 117. For example, the individualdecentralized ledger server may be dedicated to a particular shard 121of a particular blockchain 117. In some implementations, the individualdecentralized ledger server may be dedicated to a particular shard 121of a particular node 119 of a particular blockchain 117. In someimplementations, a particular blockchain 117 may be implemented bydifferent nodes 119 such that individual nodes are subsequently shardedinto multiple shards 121. Alternatively, and/or simultaneously, in someimplementations, a particular blockchain 117 may be sharded intomultiple shards 121 such that individual shards are subsequentlyimplemented by different nodes 119. This implementation may be preferredto reduce the requirements for an individual node, in particular thecommunication overhead. In implementations that use different shards121, bridge server 115 may be configured to support and/or providecommunication to and between different shards 121, to providesynchronization between different shards 121, to control operations andjoint functionality of the different shards 121, and/or otherwise manageshards 121 such that users of a particular blockchain 117 can abstractfrom the particular implementation of sharding.

Electronic storage 130 a may be similar to electronic storage 130 asdescribed elsewhere in this disclosure, though included in a particulardecentralized ledger server(s) 111. Processor(s) 132 a may be similar toprocessor(s) 132 as described elsewhere in this disclosure, thoughincluded in a particular decentralized ledger server(s) 111.Machine-readable instructions 106 a may be similar to machine-readableinstructions 106 as described elsewhere in this disclosure, thoughincluded in a particular decentralized ledger server(s) 111.

Game component 108 may be configured to execute an instance of a game(e.g., an online game within online gaming platform 105) to facilitatepresentation of the online game to users 123. In some implementations,game component 108 may be configured to implement in-game actions in theinstance of the game, e.g., in response to action requests for thein-game actions by users 123. In some implementations, game component108 may be arranged, organized, and/or otherwise included in onlinegaming platform 105. As used herein, the term “game” may refer to one ormore games within gaming platform 105. The game may be provided via avirtual space, and may include a plurality of resource types and/ormaps. An instance of the virtual space may be executed by one or morecomputer components to determine views of the virtual space. In someimplementations, the view may be communicated (e.g., by streaming, viaobject/position data, and/or other information) from server(s) 102and/or other sources to client computing platforms 104 for presentationto users 123. The view determined and transmitted to a given clientcomputing platform 104 may correspond to a location in the virtual space(e.g., the location from which the view is taken, the location the viewdepicts, and/or other locations), a zoom ratio, a dimensionality ofobjects, a point-of-view, and/or view parameters. In someimplementations, one or more view parameters may be selectable by auser.

The instance of the game may include a simulated space that isaccessible by users 123 by clients (e.g., client computing platforms104) that present the views of the virtual space to a user. Thesimulated space may have a topography, express ongoing real-timeinteraction by one or more users 123, and/or include one or more objectspositioned within the topography that are capable of locomotion and/ormovement within the topography. In some implementations, the topographymay be a 2-dimensional topography. In some implementations, thetopography may be a 3-dimensional topography. The topography may includedimensions of the simulated space, and/or surface features of a surfaceor objects that are native to the simulated space. In someimplementations, the topography may include a surface (e.g., a groundsurface) that runs through at least a substantial section of thesimulated space. In some implementations, the topography may describe avolume with one or more bodies positioned therein. The instance executedby the computer components may be synchronous, asynchronous, and/orsemi-synchronous.

Within the instance of the game, users 123 may control characters,objects, simulated physical phenomena, and/or other elements within thevirtual space to interact with the virtual space and/or each other. Theuser characters may include avatars. As used herein, the term “usercharacter” may refer to an object or group of objects present in thevirtual space, that correspond(s) to an individual user. A particularuser character may be controlled by the particular user with which it isassociated. Such user characters may be referred to as user-controlledcharacters. User-controlled element(s) may move through and interactwith the virtual space (e.g., non-user characters in the virtual space,other objects in the virtual space, etc.). User-controlled elementscontrolled by and/or associated with a given user may be created and/orcustomized by the given user. Individual users 123 may have an“inventory” of virtual goods and currency (e.g., resources of theplurality of resource types) that the individual user can use (e.g., bymanipulation of a user character and/or other user-controlled elements)and/or other items, to perform in-game actions within the virtual space.In some implementations, user inventories may be managed using one ormore decentralized ledger servers 111. For example, ownership ofindividual virtual items included in an individual user inventory may berecorded on a particular blockchain that is implemented on decentralizedledger server 111 a. In some implementations, individual userinventories (and/or digital assets therein) may correspond to individualsmart contracts stored on decentralized ledger server 111 and/orblockchain 117.

Interaction component 110 may be configured to facilitate interactionbetween users 123 within online gaming platform 105, and, in particular,within instances of the online games that are executed by game component108. For example, interaction component 110 may facilitate interactionby a particular user with other users within an instance of a particularonline game. For example, the interaction may include user-controlledin-game actions by a particular digital asset that are controlled by theparticular user. In some implementations, the interaction may occursubsequent to temporarily transferring ownership of the particulardigital asset from an original owner (e.g., to the particular user). Insome implementations, one or more particular types of interaction may befacilitated by interaction component 110. For example, interaction maybe limited to certain types of in-game actions. In some implementations,interaction may be limited to a certain time or period. In someimplementations, interaction component 110 may be arranged, organized,and/or otherwise included in online gaming platform 105.

In some implementations, interaction component 110 may facilitateinteraction by a particular user with other users within online gamingplatform 105, through a particular digital asset that is beingcontrolled by the particular user during a particular period, eventhough the particular user is not (yet) the non-temporary owner of theparticular digital asset. For example, the particular period may startwhen the particular user commits to the exchange involving theparticular digital asset, or when the particular user provides thebenefit in exchange for the particular digital asset, and/or at anotherpredefined moment during the exchange process. For example, theparticular period may end at the moment a determination has been maderegarding reversibility of the exchange involving the particular digitalasset. In some implementations, one or more types of ownership rightsare temporarily transferred to the particular user during the particularperiod. For example, one of the types of ownership rights may give theparticular user the right to use the particular digital asset in certainlimited ways. For example, usage may be limited to one or more types ofin-game actions. For example, the allowed one or more types of in-gameactions may exclude in-game actions that inflict damage to (or evendestroy) the particular digital asset.

Account component 113 may be configured to maintain user accounts forthe users of one or more decentralized ledger servers 111 and/orcomponents thereof. For example, account component 113 may maintainusers accounts for a first user, a second user, a third user, and soforth of a particular blockchain 117. In some implementations, accountcomponent 113 may maintain similar user accounts (e.g., for the same oneor more users) for different nodes 119 and/or different shards 121. Forexample, in implementations that support asset-specific sharding, thesame user may own different digital assets that are stored and/orrecorded on different nodes 119 and/or different shards 121.

Record component 112 may be configured to record rights pertaining todigital assets on one or more decentralized ledger servers 111 and/orcomponents thereof. In some implementations, record component 112 mayrecord rights on a particular blockchain 117 (or a particular shard 121,or a particular node dedicated to a particular shard 121) implementedby, e.g., decentralized ledger server 111 a. The rights may includeownership rights, distribution rights, and/or other rights. For example,particular recorded rights may reflect ownership of a particular digitalasset by a particular user. For example, the particular digital assetmay be not fungible, and may represent a three-dimensional in-gameuser-controllable character that can interact with other virtual itemswithin online gaming platform 105. Recorded rights may beasset-specific. For example, distribution rights for a particulardigital asset may designate rights to certain distributions of benefitsupon an exchange involving the particular digital asset. For example,the asset-specific distribution rights for a particular digital assetmay include one or more of (i) a right owned by a different user to apart of the benefits upon an exchange, (ii) a right owned by one or morestakeholders of online gaming platform 105 to a part of the benefitsupon an exchange, (iii) a right owned by one or more stakeholders ofbridge server 115 upon an exchange, and/or other distribution rights.These parts of a benefit may have different sizes, percentages, and/orconditions.

In some implementations, record component 112 may be configured torecord rights on blockchain 117. In some implementations, recordcomponent 112 may add, modify, and/or remove recorded rights. Forexample, in accordance with received instructions, record component 112may transfer ownership of a particular digital asset from a first ownerto a second owner (e.g., from an original owner to a new owner). In someimplementations, in accordance with received instructions, recordcomponent 112 may transfer ownership of a particular digital assettemporarily, e.g., from a first owner to a temporary second owner. Insome case, a temporary owner may be a holding account that is merelyused until ownership is transferred to either the original owner or anew owner. As used herein, the term “temporary” (and derivativesthereof) may refer to a transfer or to ownership that is either known tobe changed and/or modified within a predetermined period, or expected tobe changed and/or modified within a predetermined period. Conversely, anon-temporary transfer from a first owner to a second owner (due to aparticular exchange) can conceivably be changed and/or reverted (backfrom the second owner to the first owner) due to a separate and newexchange that is independent of the first particular exchange. In someimplementations, in accordance with received instructions, recordcomponent 112 may transfer ownership of a particular digital assetnon-temporarily from a first owner to a second owner, e.g., when aparticular exchange is not reversible or no longer reversible. In someimplementations, record component 112 may be arranged, organized, and/orotherwise included in one or more decentralized ledger servers 111. Achange and/or other modification of recorded rights (e.g., ownershiprights) may cause one or more transfers and/or transactions betweendifferent shards 121. For example, due a change in ownership, rightspertaining to a particular in-game digital asset may be moved from afirst shard to a second shard. For example, due a change in ownership,rights pertaining to a particular in-game digital asset may be movedfrom a first node of a first shard to a second node of a second shard(e.g., of the same blockchain).

Instruction component 114 may be configured to receive (sets of)instructions. Instruction component 114 may be configured to receive(sets of) instructions for execution. In some implementations,instruction component 114 may be configured to receive instructions toadd, modify, and/or remove recorded rights in one or more decentralizedledger servers 111 and/or components thereof. For example, instructioncomponent 114 may receive one or more sets of instructions from, e.g.,bridge server 115. In some implementations, instruction component 114may provide received sets of instructions to record component 112 forexecution. In some implementations, instruction component 114 may bearranged, organized, and/or otherwise included in a particulardecentralized ledger server 111 and/or components thereof.

Exchange request component 116 may be configured to receive exchangerequests from users. An exchange request may indicate a particular useroffers a particular digital asset for a transferal to another user. Atransferal may be due to different types of events, including but notlimited to a gift, a sale, theft, and/or other events. In someimplementations, an exchange request may indicate a particular useroffers a particular digital asset for a reversible exchange, e.g., on afiat-currency-based online exchange platform (e.g., online exchangeplatform 127). In some implementations, bridge server 115 may beconfigured to keep track on which particular shard 121 the ownershiprights to a particular digital asset are recorded. In someimplementations, online gaming platform 105 may be configured to keeptrack on which particular shard 121 the ownership rights to a particulardigital asset are recorded.

Rights component 118 may be configured to obtain asset-specific rights(e.g., ownership rights, distribution rights, and/or other rights) forparticular digital assets. In some implementations, rights component 118may be configured to access one or more decentralized ledger servers 111(or components thereof) to obtain the asset-specific rights (that arerecorded, e.g., in one or more smart contracts). In someimplementations, rights component 118 may be configured to obtaindifferent sets of rights (at different moments) for the same particulardigital asset. For example, rights component 118 may obtain a first setof rights at a first moment during a particular exchange, a second setof rights at a second moment (different from the first moment) duringthe same particular exchange, and so forth. For example, the rights to agiven digital asset as recorded on blockchain 117 may include a firstand second distribution right as follows: a 5% distribution right for auser (e.g., the user who designed the particular three-dimensionalin-game user-controllable character that is represented by the givendigital asset), and a 1% distribution right for a stakeholder of onlinegaming platform 105, and these distribution rights may be exercised uponcompletion of an exchange of the given digital asset. In someimplementations, rights component 118 may be configured to determinewhether rights to a newly created digital asset are recorded on a firstshard 121 or a second shard 121.

Transferal component 124 may be configured to receive transferalinformation regarding transferals of digital assets. In someimplementations, transferal component 124 may receive transferalinformation related to transferals between different users as describedin relation to the operation of exchange request component 116. In someimplementations, transferal component 124 may be configured to receiveinformation from one or more decentralized ledger servers 111 and/orcomponents thereof. Alternatively, and/or simultaneously, transferalcomponent 124 may be configured to receive information from onlinegaming platforms 105 and/or online exchange platforms 127. In someimplementations, transferal information may be asset-specific,transfer-specific, and/or exchange-specific. For example, particularreceived transferal information may be regarding a particular transferalof a particular digital asset for a particular benefit. For example, auser may have accepted an offer for exchanging the particular digitalasset for $100. In some implementations, transferal component 124 may beconfigured to receive benefits that correspond to particulartransferals. For example, the received transferal information mayinclude the particular benefit. In some implementations, the receivedtransferal information may be related to received benefit. For example,a particular received benefit may correspond to a particular transferal.

Transfer component 128 may be configured to transfer (sets of)instructions to one or more decentralized ledger servers 111 and/orcomponents thereof (including but not limited to instruction component114 for execution). For example, transfer component 128 may transfer afirst set of instructions to a first decentralized ledger server (e.g.,decentralized ledger server 111 a) and a second set of instructions to asecond decentralized ledger server (e.g., decentralized ledger server111 b). For example, when a particular digital asset is to be movedbetween different shards 121, the first set of instructions may, ineffect, remove the particular digital asset from the set of recordeddigital assets recorded on a first shard 121, and the second set ofinstructions may, in effect, add the particular digital asset to the setof recorded digital assets recorded on a second shard 121.

Node component 120 may be configured to interact with one or more nodes119. In some implementations, node component 120 may interact with afirst node 119 that is dedicated to a first shard 121 of a particularblockchain 117. At the same time, node component 120 may interact with asecond node 119 that is dedicated to a second shard 121 of the sameparticular blockchain 117. An individual shard 121 may be configured tomaintain user accounts, record rights pertaining to digital assets,receive instructions from bridge server 115 to modify recorded rights,and/or perform other operations pertaining to the individual shard 121and/or to an individual node 119 dedicated to the individual shard 121.

Translate component 126 may be configured to translate and/or convertin-game actions that have occurred on online gaming platform 105 intoone or more transactions that are (to be) recorded on one or moreparticular shards. For example, a gift of a particular digital assetwithin a game (hosted on online gaming platform 105) may be translatedinto a first transaction to be recorded on a first shard 121 and asecond transaction to be recorded on a second shard 121. For example, adiscovery or purchase of a new particular digital asset within aparticular game may be translated into a transaction to be recorded on aparticular shard 121, e.g., to issue the particular asset using afunction of a particular smart contract that creates the particularasset. For example, the destruction of a particular digital asset withina particular game may be translated into a transaction to be recorded ona particular shard 121, e.g., to burn the particular asset using afunction of the same smart contract that was used to create or issue theparticular asset. In some implementations, translate component 126 maybe configured to translate and/or convert between user identifierswithin online gaming platform 105 and user identifiers (e.g., useraccount identifiers or user account addresses) within blockchain 117. Insome implementations, translate component 126 may be configured totranslate and/or convert between asset identifiers within online gamingplatform 105 and asset identifiers within blockchain 117 (for assetsthat are not fungible).

Authorization component 136 may be configured to receive informationand/or authorization from users 123. In some implementations, thereceived authorization may pertain to one or more other steps and/ormoments during the process of a transferal or exchange. In someimplementations, authorization component 136 may receive authorizationfrom the original owner before completion of a transferal.

By way of non-limiting example, FIG. 3 illustrates an exemplary timingdiagram 30 of actions as may occur in a system similar to or the same assystem 100. A first action in timing diagram 30 represents an exchangerequest 31 from a user 11 to one or more of online gaming platform 105and/or bridge server 115. Subsequent to request 31, transferalinformation 32 is received by bridge server 115. Bridge server 115provides a first set of instructions 33 to a first decentralized ledgerserver 111 (e.g., 111 a in FIG. 1), and a second set of instructions 34to a second decentralized ledger server 111 (e.g., 111 b in FIG. 1). Inaccordance with the received set of instructions, the ownership rightsof a particular in-game digital asset are removed from the firstdecentralized ledger server 111 (e.g., 111 a in FIG. 1), and added tothe second decentralized ledger server 111 (e.g., 111 b in FIG. 1).Information 35 may be exchanged between bridge server 115 and onlinegaming platform 105 to confirm and/or provide a notification regardingthe transferal of the particular digital asset. Information 36 may beprovided to user 12 as the new owner of the particular digital asset. Insome implementations, the receipt of transferal information 32 may occursubsequent to receipt of information 32 a by bridge server 115, fromonline exchange platform 127, e.g., in case of a sales transactioninvolving the particular digital asset. In turn, the receipt ofinformation 32 a may occur subsequent to receipt of information 32 b byonline exchange platform 127, from user 12, e.g., in case of a paymentby user 12. In some implementations, user 11 may be notified uponcompletion of the transferal of the particular digital asset. Actions inaccordance with this disclosure may include additional and/or differentactions and/or steps then depicted in FIG. 3, which is merely intendedto be exemplary.

By way of non-limiting example, FIG. 4A illustrates a shard 121 a of aparticular blockchain that implements part of a blockchain including ablock 0, a block 1, and a block 2. As time progresses, more blocks maybe added to shard 121 a. The blocks within shard 121 a are ordered. Asshown in block 0, three assets (indicated by a capital “A” or “C”) arecreated and/or generated, and subsequently assigned to three users orplayers: a first asset is assigned to user i (Ui), a second asset isassigned to user j (Uj), and a third asset is a smart contract 41(indicated by a capital “C”) that is assigned to or owned by user q(Uq). Smart contract 41 may implement a limited number of digital assetsof a given type “X”. A function call to a function defined by smartcontract 41 (e.g., to request a particular type of usage, creation,and/or issuance of a digital asset of type “X”) may be depicted and/orimplemented as a transaction (e.g., the function may be invoked inexchange for consideration). In some implementations, smart contract 41may have been posted to shard 121 a by (or on behalf of) an owner orcreator (here, user q). As used in the context of blockchains,assignments may record ownership. These assets and smart contracts maybe individually manifested, deployed, and/or instantiated through arecord component similar to record component 112 (see FIG. 1). Block 1is connected to block 0 (as indicated by a link 50 a), for example byincluding an address of block 1 in block 0, or vice versa. Likewise,block 1 is connected to block 2, as indicated by a link 50 b.

In block 1, at least one asset (labeled Ax) is assigned to user q (Uq),for example by associating an address of user q with asset Ax. Asset Axmay represent an individual digital asset of type “X”. Asset Ax may becreated and/or issued by invoking one or more function calls to smartcontract 41. In some implementations, a single function calls may issuemultiple assets of the same type to user q. Asset Ax may have associatedmetadata 52 (indicated by a capital “M”), which may include and/or linkto different types of information, including but not limited to one ormore of a name, identifier, description, an image 53, (in-game) details,certificate of authenticity, and/or other information, as depicted. Forexample, the certificate of authenticity may be a digital signature.Additionally, block 1 includes two transactions (indicated by a capital“T”): a first transaction from user i to user j, and a secondtransaction from user j to user k. Block 2 includes a first transactionfrom user j to user m, and a second transaction from user q to user n.Here, the second transaction may cause asset Ax to be removed from shard121 a and added to shard 121 b in FIG. 4B. In some implementations,based on the contents of the blocks, any user of shard 121 a and/or theparticular blockchain may determine the current assets of shard 121 a,and the balances of any user. In some implementations, the balance of aparticular user may be verified prior to adding a transaction thatreduces that particular user's balance. For example, an individual usermay not be allowed to transfer assets the individual user does not own.

By way of non-limiting example, FIG. 4B illustrates a shard 121 b of theparticular blockchain that includes block 3, block 4, block 5. Block 3may be connected to some previous block as indicated by a link 50 c,block 4 may be connected to block 3 (as indicated by a link 50 d), andblock 5 may be connected to block 4 (as indicated by a link 50 e). Inblock 3, asset Ax (having associated metadata 44) of type “X” is issuedto user n (Un) and thus added to shard 121 b, due to the transactionfrom user q to user n as described for shard 121 a (i.e., thisparticular asset was removed from shard 121 a). Block 4 includes twotransactions (indicated by a capital “T”): a first transaction from useri to user n. For example, the transaction may represent a purchase of afirst virtual item by user n. Additionally, block 4 includes a secondtransaction from user q to the same smart contract as depicted in block0. For example, the second transaction may represent user q offering toexchange a different digital asset of the given type “X” for aparticular benefit (assuming user q owns another digital asset of thistype). A user who agrees to provide the requested particular benefit mayreceive limited and temporary ownership rights to this different digitalasset (whether this happens is not depicted in FIG. 4B). Block 5includes a transaction (indicated by a capital “T”), representing atransfer of ownership of the particular digital asset of the given type“X” from owner user n to new owner user p. For example, the transactionin block 5 may be completed within shard 121 b such that ownershiprights to the particular digital asset remain within shard 121 b. Insuch a case, no asset will need to be removed from shard 121 b or addedto another shard. In some implementations, decisions regarding withshard a particular digital asset will be recorded on may be made bybridge server 115.

Referring to FIG. 1, user interfaces 125 may be configured to facilitateinteraction between users 123 and system 100 and/or between users 123and client computing platforms 104. For example, user interfaces 125 mayprovide an interface through which users 123 may provide information toand/or receive information from system 100. In some implementations,user interface 125 may include one or more of a display screen,touchscreen, monitor, a keyboard, buttons, switches, knobs, levers,mouse, microphones, sensors to capture voice commands, sensors tocapture body movement, sensors to capture hand and/or finger gestures,and/or other user interface devices configured to receive and/or conveyuser input. In some implementations, one or more user interfaces 125 maybe included in one or more client computing platforms 104. In someimplementations, one or more user interfaces 125 may be included insystem 100. In some implementations, user interface 125 may be a type ofinterface that facilitates the exchange of virtual items between users.

Referring to FIG. 1, in some implementations, server(s) 102, clientcomputing platform(s) 104, and/or external resources 128 may beoperatively linked via one or more electronic communication links. Forexample, such electronic communication links may be established, atleast in part, via one or more networks 13, including but not limited tothe Internet and/or other networks. It will be appreciated that this isnot intended to be limiting, and that the scope of this disclosureincludes implementations in which server(s) 102, client computingplatform(s) 104, and/or external resources 128 may be operatively linkedvia some other communication media.

A given client computing platform 104 may include one or more processorsconfigured to execute computer program components. The computer programcomponents may be configured to enable an expert or user associated withthe given client computing platform 104 to interface with system 100and/or external resources 128, and/or provide other functionalityattributed herein to client computing platform(s) 104. By way ofnon-limiting example, the given client computing platform 104 mayinclude one or more of a desktop computer, a laptop computer, a handheldcomputer, a tablet computing platform, a NetBook, a Smartphone, a smartwatch, a gaming console, and/or other computing platforms.

External resources 138 may include sources of information outside ofsystem 100, external entities participating with system 100, and/orother resources. For example, in some implementations, externalresources 138 may include an online financial platform through whichusers may access financial information and/or perform financialtransactions. In some implementations, some or all of the functionalityattributed herein to external resources 138 may be provided by resourcesincluded in system 100.

Server(s) 102 may include electronic storage 130, one or more processors132, and/or other components. Server(s) 102 may include communicationlines, or ports to enable the exchange of information with a networkand/or other computing platforms. Illustration of server(s) 102 in FIG.1 is not intended to be limiting. Server(s) 102 may include a pluralityof hardware, software, and/or firmware components operating together toprovide the functionality attributed herein to server(s) 102. Forexample, server(s) 102 may be implemented by a cloud of computingplatforms operating together as server(s) 102.

Electronic storage 130 may comprise non-transitory storage media thatelectronically stores information. The electronic storage media ofelectronic storage 130 may include one or both of system storage that isprovided integrally (i.e., substantially non-removable) with server(s)102 and/or removable storage that is removably connectable to server(s)102 via, for example, a port (e.g., a USB port, a firewire port, etc.)or a drive (e.g., a disk drive, etc.). Electronic storage 130 mayinclude one or more of optically readable storage media (e.g., opticaldisks, etc.), magnetically readable storage media (e.g., magnetic tape,magnetic hard drive, floppy drive, etc.), electrical charge-basedstorage media (e.g., EEPROM, RAM, etc.), solid-state storage media(e.g., flash drive, etc.), and/or other electronically readable storagemedia. Electronic storage 130 may include one or more virtual storageresources (e.g., cloud storage, a virtual private network, and/or othervirtual storage resources). Electronic storage 130 may store softwarealgorithms, information determined by processor(s) 132, informationreceived from server(s) 102, information received from client computingplatform(s) 104, and/or other information that enables server(s) 102 tofunction as described herein.

Processor(s) 132 may be configured to provide information processingcapabilities in server(s) 102. As such, processor(s) 132 may include oneor more of a digital processor, an analog processor, a digital circuitdesigned to process information, an analog circuit designed to processinformation, a state machine, and/or other mechanisms for electronicallyprocessing information. Although processor(s) 132 is shown in FIG. 1 asa single entity, this is for illustrative purposes only. In someimplementations, processor(s) 132 may include a plurality of processingunits. These processing units may be physically located within the samedevice, or processor(s) 132 may represent processing functionality of aplurality of devices operating in coordination. Processor(s) 132 may beconfigured to execute components 108, 110, 112, 113, 114, 116, 118, 120,124, 126, 128, and/or 136, and/or other components. Processor(s) 132 maybe configured to execute components 108, 110, 112, 113, 114, 116, 118,120, 124, 126, 128, and/or 136, and/or other components by software;hardware; firmware; some combination of software, hardware, and/orfirmware; and/or other mechanisms for configuring processingcapabilities on processor(s) 132. As used herein, the term “component”may refer to any component or set of components that perform thefunctionality attributed to the component. This may include one or morephysical processors during execution of processor readable instructions,the processor readable instructions, circuitry, hardware, storage media,or any other components.

It should be appreciated that although components 108, 110, 112, 113,114, 116, 118, 120, 124, 126, 128, and/or 136 are illustrated in FIG. 1as being implemented within particular components, in implementations inwhich processor(s) 132 includes multiple processing units, one or moreof components 108, 110, 112, 113, 114, 116, 118, 120, 124, 126, 128,and/or 136 may be implemented remotely from the other components. Thedescription of the functionality provided by the different components108, 110, 112, 113, 114, 116, 118, 120, 124, 126, 128, and/or 136described below is for illustrative purposes, and is not intended to belimiting, as any of components 108, 110, 112, 113, 114, 116, 118, 120,124, 126, 128, and/or 136 may provide more or less functionality than isdescribed. For example, one or more of components 108, 110, 112, 113,114, 116, 118, 120, 124, 126, 128, and/or 136 may be eliminated, andsome or all of its functionality may be provided by other ones ofcomponents 108, 110, 112, 113, 114, 116, 118, 120, 124, 126, 128, and/or136. As another example, processor(s) 132 may be configured to executeone or more additional components that may perform some or all of thefunctionality attributed below to one of components 108, 110, 112, 113,114, 116, 118, 120, 124, 126, 128, and/or 136.

FIG. 2 illustrates a method 200 for operating a bridge server to supportmultiple shards of blockchains, wherein the multiple shards are used torecord ownership rights of in-game digital assets, wherein the in-gamedigital assets are usable in an online gaming platform, in accordancewith one or more implementations. The operations of method 200 presentedbelow are intended to be illustrative. In some implementations, method200 may be accomplished with one or more additional operations notdescribed, and/or without one or more of the operations discussed.Additionally, the order in which the operations of method 200 areillustrated in FIG. 2 and described below is not intended to belimiting.

In some implementations, method 200 may be implemented in one or moreprocessing devices (e.g., a digital processor, an analog processor, adigital circuit designed to process information, an analog circuitdesigned to process information, a state machine, and/or othermechanisms for electronically processing information). The one or moreprocessing devices may include one or more devices executing some or allof the operations of method 200 in response to instructions storedelectronically on an electronic storage medium. The one or moreprocessing devices may include one or more devices configured throughhardware, firmware, and/or software to be specifically designed forexecution of one or more of the operations of method 200.

At an operation 202, an instance of a first online game is executed tofacilitate presentation of the first online game to users, and in-gameactions are implemented in the instance of the first online game inresponse to action requests for the in-game actions by the users. Thepresentation of the first online game includes the presentation of viewsof the first online game that are determined using information generatedby execution of the instance of the first online game. The users includea first user and a second user that interact with the online gamingplatform. In some embodiments, operation 202 is performed by a gamecomponent the same as or similar to game component 108 (shown in FIG. 1and described herein).

At an operation 204, user accounts are maintained, by a firstdecentralized ledger that implements a first node of a first shard of afirst blockchain, for the users of the first blockchain, including thefirst user and the second user. In some embodiments, operation 204 isperformed by an account component the same as or similar to accountcomponent 113 (shown in FIG. 1 and described herein).

At an operation 206, on the first shard, a first set of rights isrecorded pertaining to a first set of digital assets. The recorded firstset of rights reflect ownership of a first digital asset by the firstuser. The first digital asset is usable within the online gamingplatform. In some embodiments, operation 206 is performed by a recordcomponent the same as or similar to record component 112 (shown in FIG.1 and described herein).

At an operation 208, by the first decentralized ledger, instructions arereceived to modify the recorded first set of rights. In someembodiments, operation 208 is performed by an instruction component thesame as or similar to instruction component 114 (shown in FIG. 1 anddescribed herein).

At an operation 210, user accounts are maintained by a seconddecentralized ledger that implements a second node of a second shard ofthe first blockchain, for the users of the first blockchain, includingthe first user and the second user. In some embodiments, operation 210is performed by an account component the same as or similar to accountcomponent 113 (shown in FIG. 1 and described herein).

At an operation 212, on the second shard, a second set of rights isrecorded pertaining to a second set of digital assets. The recordedsecond set of rights reflect ownership of a second digital asset by thefirst user. The second digital asset is usable within the online gamingplatform. In some embodiments, operation 212 is performed by a recordcomponent the same as or similar to record component 112 (shown in FIG.1 and described herein).

At an operation 214, by the second decentralized ledger, instructionsare received to modify the recorded second set of rights. In someembodiments, operation 214 is performed by an instruction component thesame as or similar to instruction component 114 (shown in FIG. 1 anddescribed herein).

At an operation 216, from the first user, an exchange request isreceived that indicates the first user offers the first digital assetfor a first transferal to one of the users. In some embodiments,operation 216 is performed by an exchange request component the same asor similar to exchange request component 116 (shown in FIG. 1 anddescribed herein).

At an operation 218, transferal information is received regarding thefirst transferal of the first digital asset from the first user to thesecond user. In some embodiments, operation 218 is performed by atransferal component the same as or similar to transferal component 124(shown in FIG. 1 and described herein).

At an operation 220, responsive to receipt of the transferalinformation, a first set of instructions is transferred to the firstdecentralized ledger server and a second set of instructions to thesecond decentralized ledger server. In some embodiments, operation 220is performed by a transfer component the same as or similar to transfercomponent 128 (shown in FIG. 1 and described herein).

At an operation 222, the first set of instructions is received. In someembodiments, operation 222 is performed by an instruction component thesame as or similar to instruction component 114 (shown in FIG. 1 anddescribed herein).

At an operation 224, in accordance with the received first set ofinstructions, the first digital asset is removed from the first set ofdigital assets, such that the recorded first set of rights on the firstshard no longer reflect the ownership of the first digital asset by thefirst user. In some embodiments, operation 224 is performed by a recordcomponent the same as or similar to record component 112 (shown in FIG.1 and described herein).

At an operation 226, the second set of instructions is received. In someembodiments, operation 226 is performed by an instruction component thesame as or similar to instruction component 114 (shown in FIG. 1 anddescribed herein).

At an operation 228, in accordance with the received second set ofinstructions, the first digital asset is added to the second set ofdigital assets, such that the recorded second set of rights on thesecond shard reflect the ownership of the first digital asset by thesecond user. In some embodiments, operation 228 is performed by a recordcomponent the same as or similar to record component 112 (shown in FIG.1 and described herein).

Although the present technology has been described in detail for thepurpose of illustration based on what is currently considered to be themost practical and preferred implementations, it is to be understoodthat such detail is solely for that purpose and that the technology isnot limited to the disclosed implementations, but, on the contrary, isintended to cover modifications and equivalent arrangements that arewithin the spirit and scope of the appended claims. For example, it isto be understood that the present technology contemplates that, to theextent possible, one or more features of any implementation can becombined with one or more features of any other implementation.

1. A system configured for operating a bridge server to support multipleasset-specific shards of blockchains while limiting overhead forcommunication between different ones of the multiple asset-specificshards, wherein the multiple asset-specific shards are used to recordownership rights of different and mutually exclusive sets of in-gamedigital assets, wherein the in-game digital assets are usable in anonline gaming platform, comprising: an online gaming platform configuredto host one or more games, the online gaming platform including one ormore processors configured by machine-readable instructions to: executean instance of a first online game, and present the first online game tousers, wherein presenting the first online game includes presentation ofviews of the first online game that are determined during execution ofthe instance of the first online game, wherein the users include a firstuser and a second user; a first decentralized ledger server configuredto implement a first node of a first shard of a first blockchain,wherein the first decentralized ledger server includes one or moreprocessors configured by machine-readable instructions to: maintain useraccounts for the users of the first blockchain, including the first userand the second user; record, on the first shard, a first set of rightspertaining to a first set of digital assets owned by different users,wherein the first set of digital assets includes a first digital asset,wherein the recorded first set of rights reflect ownership of the firstdigital asset by the first user, wherein the first digital asset isconfigured to be used within the online gaming platform; and receiveinstructions to modify the recorded first set of rights with regard tothe ownership of the first digital asset; a second decentralized ledgerserver configured to implement a second node of a second shard of thefirst blockchain, wherein the second decentralized ledger serverincludes one or more processors configured by machine-readableinstructions to: maintain user accounts for the users of the firstblockchain, including the first user and the second user; record, on thesecond shard, a second set of rights pertaining to a second set ofdigital assets owned by the different users, wherein the second set ofdigital assets is mutually exclusive with the first set of digitalassets; and receive instructions to modify the recorded second set ofrights pertaining to one or more digital assets in the second set ofdigital assets; the bridge server, including one or more processorsconfigured by machine-readable instructions to: receive, on behalf ofthe first user, an exchange request that indicates that the first useroffers the ownership of the first digital asset for a first transferalfrom the first user to the second user; receive transferal informationregarding the first transferal of the ownership of the first digitalasset from the first user to the second user; responsive to receipt ofthe transferal information regarding the first transferal of theownership of the first digital asset from the first user to the seconduser, transfer a first set of instructions to the first decentralizedledger server and a second set of instructions to the seconddecentralized ledger server; wherein the one or more processors of thefirst decentralized ledger server are further configured to (i) receivethe first set of instructions from the bridge server, and (ii) inaccordance with the received first set of instructions, remove the firstdigital asset from the recorded first set of digital assets on the firstshard, such that, subsequent to removal of the first digital asset, therecorded first set of rights on the first shard no longer reflect theownership of the first digital asset as being owned by the first user;and wherein the one or more processors of the second decentralizedledger server are further configured to (i) receive the second set ofinstructions from the bridge server, and (ii) in accordance with thereceived second set of instructions, add the first digital asset to therecorded second set of digital assets on the second shard as being ownedby the second user, such that, subsequent to addition of the firstdigital asset, the recorded second set of rights on the second shardreflect the ownership of the first digital asset as being owned by thesecond user, and further such that the recorded first set of digitalassets on the first shard remains mutually exclusive with the recordedsecond set of digital assets on the second shard.
 2. (canceled)
 3. Thesystem of claim 1, wherein the first node is dedicated to the firstshard, and wherein the second node is dedicated to the second shard ofthe first blockchain.
 4. The system of claim 1, wherein the firstdigital asset represents a three-dimensional in-game user-controllablecharacter configured to interact with other virtual items within theonline gaming platform, wherein the first digital asset is not fungible.5. (canceled)
 6. The system of claim 1, wherein the one or moreprocessors included in the bridge server are further configured by themachine-readable instructions such that the exchange request is receivedfrom the online gaming platform.
 7. The system of claim 1, wherein theone or more processors included in the bridge server are furtherconfigured by the machine-readable instructions to translate one or morein-game actions that have occurred on the online gaming platform intoone or more transactions that are recorded on one or both of the firstshard and the second shard.
 8. The system of claim 1, wherein the one ormore processors included in the bridge server are further configured bythe machine-readable instructions to: create a new digital asset; anddetermine whether rights to the new digital asset are recorded on thefirst shard or the second shard.
 9. A method for operating a bridgeserver to support multiple asset-specific shards of blockchains, whereinthe multiple asset-specific shards are used to record ownership rightsof different and mutually exclusive sets of in-game digital assets,wherein the in-game digital assets are usable in an online gamingplatform, the method being implemented in a computer-implemented system,the method comprising: executing an instance of a first online game, andpresenting the first online game to users, wherein presenting the firstonline game includes presentation of views of the first online game thatare determined during execution of the instance of the first onlinegame, wherein the users include a first user and a second user thatinteract with the online gaming platform; maintaining, by a firstdecentralized ledger server that implements a first node of a firstshard of a first blockchain, user accounts for the users of the firstblockchain, including the first user and the second user; recording, onthe first shard, a first set of rights pertaining to a first set ofdigital assets owned by different users, wherein the first set ofdigital assets includes a first digital asset, wherein the recordedfirst set of rights reflect ownership of the first digital asset by thefirst user, wherein the first digital asset is configured to be usedwithin the online gaming platform; receiving, by the first decentralizedledger server, instructions to modify the recorded first set of rightswith regard to the ownership of the first digital asset; maintaining, bya second decentralized ledger server that implements a second node of asecond shard of the first blockchain, user accounts for the users of thefirst blockchain, including the first user and the second user;recording, on the second shard, a second set of rights pertaining to asecond set of digital assets owned by the different users, wherein thesecond set of digital assets is mutually exclusive with the first set ofdigital assets; receiving, by the second decentralized ledger server,instructions to modify the recorded second set of rights pertaining toone or more digital assets in the second set of digital assets;receiving, on behalf of the first user, an exchange request thatindicates that the first user offers the ownership of the first digitalasset for a first transferal from the first user to the second user;receiving transferal information regarding the first transferal of theownership of the first digital asset from the first user to the seconduser; responsive to receipt of the transferal information regarding thefirst transferal of the ownership of the first digital asset from thefirst user to the second user, transferring a first set of instructionsto the first decentralized ledger server and a second set ofinstructions to the second decentralized ledger server; receiving, bythe first decentralized ledger server, the first set of instructions; inaccordance with the received first set of instructions, removing thefirst digital asset from the recorded first set of digital assets on thefirst shard, such that, subsequent to removal of the first digitalasset, the recorded first set of rights on the first shard no longerreflect the ownership of the first digital asset as being owned by thefirst user; receiving, by the second decentralized ledger server, thesecond set of instructions; in accordance with the received second setof instructions, adding the first digital asset to the recorded secondset of digital assets on the second shard as being owned by the seconduser, such that, subsequent to addition of the first digital asset, therecorded second set of rights on the second shard reflect the ownershipof the first digital asset as being owned by the second user, andfurther such that the recorded first set of digital assets on the firstshard remains mutually exclusive with the recorded second set of digitalassets on the second shard; and receiving, from the second user, anaction request for an in-game action in the instance of the first onlinegame, wherein the action request pertains to control of the firstdigital asset by the second user.
 10. (canceled)
 11. The method of claim9, wherein performance of the in-game action in the instance of thefirst online game requires the ownership of the first digital asset bythe second user.
 12. The method of claim 9, wherein the first digitalasset represents a three-dimensional in-game user-controllable characterthat can interact with other virtual items within the online gamingplatform, wherein the first digital asset is not fungible. 13.(canceled)
 14. The method of claim 9, wherein the exchange request isreceived from the online gaming platform.
 15. The method of claim 9,further comprising: translating one or more in-game actions that haveoccurred on the online gaming platform into one or more transactionsthat are recorded on one or both of the first shard and the secondshard.
 16. The method of claim 9, further comprising: creating a newdigital asset; and determining whether rights to the new digital assetare recorded on the first shard or the second shard.
 17. A systemconfigured for operating a bridge server to support multiple shards ofblockchains, wherein the multiple shards are used to record ownershiprights of in-game digital assets, wherein the in-game digital assets areusable in an online gaming platform, comprising: an online gamingplatform configured to host one or more games, the online gamingplatform being provided, at least in part, by one or more game serversthat include one or more processors configured by machine-readableinstructions to: execute an instance of a first online game tofacilitate presentation of the first online game to users, and implementin-game actions in the instance of the first online game in response toaction requests for the in-game actions by the users, wherein thepresentation of the first online game includes the presentation of viewsof the first online game that are determined using information generatedby execution of the instance of the first online game, wherein the usersinclude a first user and a second user that interact with the onlinegaming platform; the bridge server, including one or more processorsconfigured by machine-readable instructions to: interact with a firstnode that is dedicated to a first shard of a first blockchain, whereinthe first shard (i) maintains user accounts for the users of the firstblockchain, including for the first user and the second user, (ii)records a first set of rights pertaining to a first set of digitalassets, wherein the recorded first set of rights reflect ownership of afirst digital asset by the first user, wherein the first digital assetis usable within the online gaming platform, and (iii) receivesinstructions from the bridge server to modify the recorded first set ofrights; interact with a second node that is dedicated to a second shardof the first blockchain, wherein the second shard (i) maintains useraccounts for the users of the first blockchain, including for the firstuser and the second user, (ii) records a second set of rights pertainingto a second set of digital assets, wherein the recorded second set ofrights reflect ownership of a second digital asset by the first user,wherein the second digital asset is usable within the online gamingplatform, and (iii) receives instructions from the bridge server tomodify the recorded second set of rights; receive, from the first user,an exchange request that indicates the first user offers the firstdigital asset for a first transferal to one of the users; receivetransferal information regarding the first transferal of the firstdigital asset from the first user to the second user; and responsive toreceipt of the transferal information, transfer a first set ofinstructions to the first node and a second set of instructions to thesecond node such that; the first node (i) receives the first set ofinstructions from the bridge server, and (ii) in accordance with thereceived first set of instructions, removes the first digital asset fromthe first set of digital assets, such that the recorded first set ofrights on the first shard no longer reflect the ownership of the firstdigital asset by the first user; and the second node (i) receives thesecond set of instructions from the bridge server, and (ii) inaccordance with the received second set of instructions, adds the firstdigital asset to the second set of digital assets, such that therecorded second set of rights on the second shard reflect the ownershipof the first digital asset by the second user.
 18. The system of claim17, wherein the first set of digital assets and the second set ofdigital assets are mutually exclusive.
 19. The system of claim 17,wherein the first digital asset represents a three-dimensional in-gameuser-controllable character that can interact with other virtual itemswithin the online gaming platform.
 20. The system of claim 17, whereinthe bridge server is further configured to: translate one or morein-game actions that have occurred on the online gaming platform intoone or more transactions that are recorded on one or both of the firstshard and the second shard; and determine whether rights to a newlycreated digital asset are recorded on the first shard or the secondshard, wherein the first and second shards are asset-specific shards.